To connect to a TCP server interface, you would naturally use the TCP client interface. Many TCP Client interfaces from different peers can connect to the same TCP Server interface at the same time.

The TCP interface types can also tolerate intermittency in the IP link layer. This means that Reticulum will gracefully handle IP links that go up and down, and restore connectivity after a failure, once the other end of a TCP interface reappears.

[[TCP Client Interface]]

type = TCPClientInterface

interface_enabled = True

target_host = 127.0.0.1

target_port = 4242

It is also possible to use this interface type to connect via other programs or hardware devices that expose a KISS interface on a TCP port, for example software-based soundmodems. To do this, use the kiss_framing option:

[[TCP KISS Interface]]

type = TCPClientInterface

interface_enabled = True

kiss_framing = True

target_host = 127.0.0.1

target_port = 8001

Caution! Only use the KISS framing option when connecting to external devices and programs like soundmodems and similar over TCP. When using the TCPClientInterface in conjunction with the TCPServerInterface you should never enable kiss_framing, since this will disable internal reliability and recovery mechanisms that greatly improves performance over unreliable and intermittent TCP links.

Please Note! The TCP interfaces support tunneling over I2P, but to do so reliably, you must use the i2p_tunneled option:

[[TCP Client over I2P]]

type = TCPClientInterface

interface_enabled = yes

target_host = 127.0.0.1

target_port = 5001

i2p_tunneled = yes

THIS IS A PART OF THE

Back to the Node Startpage